            ͻ
	    							
               Compex RL2000(A) PnP Series Ethernet Adapter    
              Copyright (C) 1998 by PDS. All Rights Reserved.  
	    							
	    ͼ


 +  How to Configure Windows 95 Remoteboot from Windows NT 4.0  +
 +  with Compex RL2000A PnP Network Adapter                     +
    ============================================================

This document provides step-by-step instructions on how to remoteboot 
Windows 95 clients with Compex RL2000A PnP network adapters from a 
Windows NT 4.0 server using the NT Remoteboot Service.
 
It is assumed that you are a network administrator or equivalent and that 
you have prior experience installing and configuring the NT Remoteboot 
Service.

What you will need.. 

* A Windows NT 4.0 server with the Remoteboot Service installed and configed.
  Earlier versions of NT do not support Windows 95 clients.

* A workstation running Windows 95 with connections to the NT server

* Window95 CD, make sure the CD-ROM contains the NETSETUP.EXE program.

* Compex RL2000A PnP network adapters with boot PROM v3.00 or higher.

  Note:- Be sure to verify that your boot PROM is configured to boot
         from LanManager/WINNT Server. To set to the correct boot protocol, 
         reset boot your PC. When the screen message "Configuring... " 
         appears, press Ctrl-Enter keys will put you to the boot protocol 
         menu. Select the LM/WINNT option. Press F2 key to save. 
	 Power OFF and ON the PC again to cold start the machine.

** IMPORTANT    **************************************
   
Before you can remoteboot Win95 client from Windows NT server, you must
first install remoteboot DOS client from Windows NT server.
Refer to the Compex driver disk remoteboot directory for details. 
Complete this step then come back and continue the steps below.  

RL2000A-PNP MUST be configured to Non-PnP mode to run.

		**************************************

To support Windows 95 remoteboot clients, you must:
   * install Server-Based Setup (SBS) on a server, 
   * install the first Windows 95 client, 
   * install subsequent clients. 


1. Installing SBS for Windows 95 Clients 
   

1.1. On the NT4.0 server, CREATE a shared directory with 90 MB space 
     available. The shared directory can have any name.
     In the example, it is C:\WIN95RB.

SHARE the directory, assign read-only permission for regular users 
and full access for administrators.

1.2. INSTALL one regular Windows 95 client on the network or use an existing
     one. LOG ON to the Windows 95 client using an account that has write 
     access to the NT4.0 shared directory C:\WIN95RB. 

1.3. Put the Windows 95 CD in the client's CD-ROM drive. In 
     Windows Explorer, SWITCH to the ADMIN\NETTOOLS\NETSETUP directory. 

1.4. Double-click NETSETUP.EXE. 

1.5. In the Server-Based Setup dialog box, click the Set Path button, and 
     then specify the path to the SBS server. Then click OK. 

You can type a drive letter for a mapped drive, a network name for a server.

In this example, 
			g:\win95rb, 

   or a network path as \\ntserver\win95rb

1.6. Click Install. Server-Based Setup presents a series of dialog boxes so 
     that you can complete these actions: 

1.6.1 Specify an "Install Policy" for how users can install Windows 95 
      from the server. If you support only remoteboot clients, choose the
      "SERVER" option.

1.6.2 Set the source path for Windows 95 files. This is the path to the 
      CD on the client.

1.6.3 Else by default

1.6.4 Provide a CD Key number for product identification. Server-Based Setup
      copies Windows 95 files to the SBS shared directory, \\ntserver\win95rb.

1.7. At the remoteboot server, put the CD or floppy disk containing the 
     Windows NT remoteboot for Windows 95 files into a drive. Change to the 
     drive and then change to the UPDATE\WIN95 directory. Run win95srv.bat to 
     update the Windows 95 files for remotebooting. For example: 

          d:\ 
          cd \update\win95
          win95srv.bat c:\win95rb

   or run,
          win95srv.bat \\netserver\win95rb

1.8. At the remoteboot server, click START and start Remoteboot Manager. 
     From the Configure menu, choose Check Configurations to activate the new 
     configurations. 


2. Creating Remoteboot Configurations for RL2000A PnP Adapters 
   

To Create a new Win95 boot block record and a configuration for RL2000A.
The following procedure should be done at the NT remoteboot server.

2.1. Copy the file W95BB.CNF from Compex Adapter Supplement disk or Compex 
     Driver Disk to the directory,

		     C:\WINNT\RPL\BBLOCK\NETBEUI\RLPNPA

2.2. Use the rplcmd utility to add a boot block record for RL2000A PnP. 
     Do as following:

c:\winnt\rpl> rplcmd 

Adapter Boot Config Profile Service Vendor Wksta [Quit]: b 

Add Del Enum: a

BootName=RL2KA_W95 

VendorName=008048 

BbcFile=BBLOCK\NETBEUI\RLPNPA\W95BB.CNF 

All other parameters are optional

BootComment=Win95 Compex RL2000A PNP adapter

WindowSize=0

Use the rplcmd utility to add a new configuration. 

Adapter Boot Config Profile Service Vendor Wksta [Quit]: c

Add Del Enum: a

ConfigName=RL2KA_W95 

BootName=RL2KA_W95

DirName=DOS

DirName2=WIN95 

FitShared=fits\win95.FIT 

FitPersonal=fits\win95p.FIT 

All other parameters are optional 

ConfigComment=Compex RL2000A PNP adapter

DirName3=

DirName4=

Adapter Boot Config Profile Service Vendor Wksta [Quit]: q

2.3. At the remoteboot server, start Remoteboot Manager. From the Configure
     menu, choose Check Configurations to activate the new configurations. 

2.4. At the Remoteboot Manager, create a Windows 95 profile for RL2000A
     adapter. Choose the menu item New Profile. Then select the configuration 
     just created as above and a name for it,
  
         e.g. RL2KAW95_1. 

3. To Install the First Windows 95 Client 
   

Installing the first Windows 95 client requires booting that client first to
MS-DOS 6.2x, running Windows 95 Setup on the client, and then copying 
selected files from the client's machine directory to the remoteboot server. 
Once you have installed this first client, you can easily install subsequent 
clients by using SBS to make a modified copy of the original machine directory
without having to run Windows 95 Setup again. 

Each remoteboot client has a "machine directory," a directory on a server 
that contains client-specific configuration information and data. 
For example, the machine directory contains the following: 

Machine directories can reside on the remoteboot server, on the SBS server, 
or on any designated server on the network. You may want to spread the load 
of machine directories across servers. The only qualifications for a machine
directory server are sufficient disk space and running the NetBEUI protocol. 

To create a location for machine directories, simply make a shared directory 
on a server and share it with a name that does not contain spaces. 
For example, on a computer running Windows NT Server that will contain 
machine directories, you create, 

	c:\win95ws 

Assign permissions to a machine directory so that only the users or 
administrators who will use the client have read and write permissions in 
the directory. If the machine directory is on an NTFS partition, assign 
permissions directly to the machine directories. If the machine directory 
is on an FAT partition, assign permissions to the shared directory containing
the machine directories. 

To install the first Windows 95 client: 


3.1. Boot the new client to MS-DOS 6.2x. Be sure to switch off the PnP.

You will need to run Windows 95 Setup while the client is booted from the 
Remoteboot Service, rather than when the client is booted from a floppy disk 
or hard drive. 

3.2. Use the net logon command to log on using an account that has read 
     access both to the SBS server NTSERVER and write access to the shared 
     directory that will contain this client's machine directory. 
     e.g. we use the same NT server NTSERVER. 

e.g. Net logon: administrator

3.3. Use the net use command to map drive letters to the SBS server and 
     machine directory location. Determine the highest drive letter in use
     on the computer.

		net use f: \\ntserver\win95rb 
		net use g: \\ntserver\win95ws

3.4.Make a temporory directory as temp,
	C:>md temp

3.5 Change to the drive letter mapped to the SBS directory.
	C:>F:

3.6 Run the Windows 95 Setup program by typing; 

	C:>setup /t:c:\temp

3.7. Make the following decisions during setup: 

* In the Server-based Setup dialog box, choose "Set up Windows to run 
  from a network server". 

* In the Startup Method dialog box, choose "Start Windows from the 
  network (remote boot server)." 

* In the Machine Directory dialog box, when asked where to install Windows 95,
  type the path of the machine directory;

	G:\WIN95.RLA 

* In the Setup Options dialog box, choose Custom setup. 

* In the Analyzing Your Computer dialog box, choose "No, I want to modify 
  the hardware list." EXCLUDE AS MANY hardware types and items from 
  autodetection as possible. If autodetection crashes, run Setup again and 
  exclude more items from autodetection.

* In the Select Components dialog box, clear the checkbox for "Communications"

* In the Network Configuration dialog box, you must add and configure your 
  network adapter as RL2000A NDIS2 driver. If you add your network adapter, you
  must confirm the resource settings for the adapter. Select the adapter name 
  in the Network Configuration dialog box, click Properties, and then click 
  the Resources tab. Check that the settings displayed are correct 
  (for example, IRQ=5,IO ADDR=200). Then, click OK to force the Setup program 
  to accept the settings; do not click Cancel.

3.7. When the Windows 95 Setup program is done, down your client. The client
     will not yet boot to Windows 95. You must complete more steps below.


4. At the remoteboot server, start Remoteboot Manager. 
   Skip step 4 if you have done this in step 2. 
   Continue if you have more than one adapter profile to create. 

4.1. Create a profile for the Windows 95 client. In the Configuration box, 
     choose the Windows 95 configuration corresponding to the client's network 
     adapter type.                    

4.2. If you are not sure which configuration to choose, check the profile 
     that is currently associated with this client for booting MS-DOS, and use 
     the equivalent Windows 95 profile. 

4.3. Edit the client's workstation record to assign the client to the 
     Windows 95 profile. 

5. At the remoteboot server DOS prompt, do the following,

	C:> cd \rpl\bin <Enter>

	C:> win95clt mach_directory \\rpl_server profile_name 
 Where, 
* mach_directory is the path to the client's machine directory.
* \\rpl_server is the name of the remoteboot server. 
* profile_name is the name of the Windows 95 profile associated with the 
  client. 

For the case, you type: 
	C:>cd \winnt\rpl\bin <Enter> 
	C:>win95clt c:\win95ws\win95.rla \\ntserver rl2kaw95_1
  or
        C:>win95clt \\ntserver\win95ws\win95.2ka \\ntserver rl2kaw95_1

** As the win95 profile(eg. rl2kaw95_1) can be shared by the same model 
   card with same IO Addr/IRQ and same driver, otherwise you must create
   a new profile for the card.

6. At the SBS server, edit the MACHINES.INI file in the SBS directory, in the
   case NTSERVER\\WIN95RB. Add the following lines for the client: 

	[adapter id] 
	SYSDATPATH=g:\machine_dir 
	g:=\\mach_server\mach_share 

Where: 
* adapter id is the network adapter id, specified in the remoteboot workstation
  record for this client. 

* \machine_dir is the location of the client's machine directory on a server. 

* g: is the drive letter assigned on the next line to the shared directory 
  where the client's machine directory is located. 

* \\mach_server\mach_share identifies the drive letter assigned to the shared directory where the machine directory resides. You must use the same drive letter and share name established in Step 4. 

For example, you might add the following lines to MACHINES.INI: 

	[008048ED1234]
	SYSDATPATH=g:\win95.rla
	g:=\\ntserver\win95ws

7. Reboot the Windows 95 client. The client will now boot to Windows 95 and 
   complete the Windows 95 Setup program.

7.1. What You See on a Windows 95 Client

When you boot the client, a remoteboot logon prompt appears:

Type Remoteboot username, or press enter if it is <workstation>: 

This asks for the account name and password associated with the client 
computer itself, NOT for your own user account name and password.

Windows 95 then prompts you twice for your user name and password: once from
a command prompt and again in a dialog box. At both of these prompts, enter
your user account name and password. e.g. administrator.

                      -----------------------------



